Customer controlled interaction management

ABSTRACT

A system and method for managing interactions of a customer contact center. A contact center processor receives a request to reserve a contact center resource for handling an interaction. The processor also receives data about the interaction. The processor identifies a routing point for routing the interaction based on the received data. The routing point is associated with routing logic controlled by a customer instead of the contact center. The processor routes the interaction to the identified routing point for giving the customer control of the routing of the interaction.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/594,211, filed on May 12, 2017, now U.S. Pat. No. 9,900,437, which isa continuation of U.S. patent application Ser. No. 14/470,898, filed onAug. 27, 2014, now U.S. Pat. No. 9,654,637, which is related to U.S.patent application Ser. No. 14/470,913, filed on Aug. 27, 2014, thecontent of all of which are incorporated herein by reference.

BACKGROUND

Typical processing of interactions between a customer and a contactcenter are generally under the control of the contact center. Forexample, the contact center generally selects the agent to which aninbound/outbound interaction from/to a customer is to be routed.Although contact centers do employ certain business driven customizationand personalization, such customization and personalization generallysides with the interests of the business.

There are some instances where the customer has access to a direct phoneline of the customer's preferred agent and may therefore be in controlof the agent with whom the customer ultimately interacts. However, evenin this scenario, the customer runs the risk of dialing “blindly”without knowledge of the availability of the agent to answer the call.

Accordingly, what is need is a system and method for providing acustomer at least partial control of interactions with a contact center.

SUMMARY

Embodiments of the present invention are directed to system and methodfor managing interactions of a customer contact center. The systemincludes a processor and a memory. The memory has stored thereininstructions that, when executed by the processor, cause the processorto execute the following acts. The processor receives a request toreserve a contact center resource for handling an interaction. Theprocessor also receives data about the interaction. The processoridentifies a routing point for routing the interaction based on thereceived data. The routing point is associated with routing logiccontrolled by a customer instead of the contact center. The processorroutes the interaction to the identified routing point for giving thecustomer control of the routing of the interaction.

According to one embodiment, the interaction is a telephony interaction,and the system includes a switch that is coupled to the processor forestablishing a voice path between the end user device and a device ofthe contact center resource.

According to one embodiment, the received data includes a calleridentifier.

According to one embodiment, the processor transmits a softwareapplication to the customer end user device over a communicationsnetwork, where the software application includes instructions forexecuting the routing logic.

According to one embodiment, the software application monitors presenceof the contact center resource.

According to one embodiment, the software application includesinstructions for receiving the presence information from a contactcenter server.

According to one embodiment, the software application is transmitted tothe customer end user device in response to identifying the customer asbelonging to a particular customer segment.

According to one embodiment, the interaction is a telephony interaction,and the software application invokes a dialer for initiating thetelephony interaction.

According to one embodiment, the software application provides aninterface for prompting the customer to configure the routing logic.

According to one embodiment, the software application provides aninterface for prompting the customer to identify one or more preferredcontact center agents.

According to one embodiment, the software application provides aninterface for prompting the customer to rate the interaction.

According to one embodiment, the software application is configured toshare the rating with other customers.

According to one embodiment, the routing point is identified by atelephone number.

These and other features, aspects and advantages of the presentinvention will be more fully understood when considered with respect tothe following detailed description, appended claims, and accompanyingdrawings. Of course, the actual scope of the invention is defined by theappended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the present invention, and many of theattendant features and aspects thereof, will become more readilyapparent as the invention becomes better understood by reference to thefollowing detailed description when considered in conjunction with theaccompanying drawings in which like reference symbols indicate likecomponents, wherein:

FIG. 1 is a schematic block diagram of a generalized system for customercontrolled interaction management according to one embodiment of theinvention;

FIG. 2 is a more detailed block diagram of the contact center componentsaccording to one exemplary embodiment of the invention;

FIG. 3 is a more detailed block diagram of a client iXn controller and acontact center (CC) iXn controller according to one embodiment of theinvention;

FIG. 4 is a more detailed block diagram of a client iXn controller and aCC iXn controller according to another embodiment of the invention;

FIG. 5 is a more detailed block diagram of a client iXn controller and aCC iXn controller according to another embodiment of the invention;

FIG. 6 is a more detailed block diagram of a client iXn controller and aCC iXn controller according to another embodiment of the invention;

FIG. 7 is a flow diagram of a process executed by a client iXncontroller to allow customer controlled interaction management for acustomer according to one embodiment of the invention;

FIG. 8 is a flow diagram of a process executed by the CC iXn controllerto allow customer controlled interaction management for a customeraccording to one embodiment of the invention;

FIGS. 9A-9B are exemplary signaling diagrams of messages exchangedbetween an end user and the contact center system in a non-CCIM enabledinteraction according to one embodiment of the invention;

FIG. 10A is a block diagram of a computing device according to anembodiment of the present invention;

FIG. 10B is a block diagram of a computing device according to anembodiment of the present invention;

FIG. 10C is a block diagram of a computing device according to anembodiment of the present invention;

FIG. 10D is a block diagram of a computing device according to anembodiment of the present invention; and

FIG. 10E is a block diagram of a network environment including severalcomputing devices according to an embodiment of the present invention.

DETAILED DESCRIPTION

In general terms, embodiments of the present invention are directed to asystem and method for customer controlled interaction management (CCIM)where a customer is given control of interactions with a contact centerwhere such control would typically reside with the contact center.According to one embodiment, the control exercised by the customer isthe routing of interactions to contact center resources (e.g. agents).In giving a customer CCIM for an interaction, the contact center exposesreal-time status information of certain resources of the contact center,such as, for example, presence information of certain agents of thecontact center. Based on this information, the customer dictates when toinitiate the interaction, and the selection of the agent to whom theinteraction is to be routed. In this regard, the traditional role of thecontact center (business) and the customer are reversed. Instead of thecontact center acting in the best interest of the contact center, thecustomer controls interactions according to his best interest.

According to one embodiment, CCIM eligibility may be given for certaintypes of customers, such as, for example, customers deemed to beimportant to the contact center. For example, CCIM eligibility may begiven to customers in certain customer segments (e.g. customers labeledas “Gold” customers). In some embodiments, CCIM eligibility may beprovided as compensation for bad customer service experience. Also, insome embodiments, CCIM eligibility may be revoked by the contact center.

By enabling CCIM for “Gold” customers, the need for agent reservationfor such customers is reduced if not eliminated. CCIM may allow such a“Gold” customer to experience the same or even better customerexperience than what would be achieved by having dedicated, reservedagents for such customers, while at the same time, avoiding the risk ofsuch reserved agents sitting idle when there is traffic overload forother agents. CCIM also allows the reduction or avoidance of callparking (queuing) at the business by establishing the call only when thedesired agent is actually available. If there is some waiting involvedfor a CCIM session, it may not count towards meeting the business'service level, allowing service compliance for CCIM sessions to berelaxed.

FIG. 1 is a schematic block diagram of a generalized system for customercontrolled interaction management according to one embodiment of theinvention. The system includes an end user device 10 coupled to acontact center system 12 over a communications network 14 conventionalin the art. For example, the communications network 14 may include aprivate or public switched telephone network (PSTN), local area network(LAN), private wide area network (WAN), and/or public wide area networksuch as, for example, the Internet. The communications network 14 mayalso include a wireless carrier network including a code divisionmultiple access (CDMA) network, global system for mobile communications(GSM) network, or any wireless network/technology conventional in theart, including but to limited to 3G, 4G, LTE, and the like.

According to one embodiment, the end user device 10 may be acommunication device conventional in the art, such as, for example, asmart phone, laptop, desktop, electronic tablet, and/or the like. Acustomer operating the end user device 10 may initiate, manage, andrespond to telephone calls, emails, chats, text messaging, web-browsingsessions, and other multi-media transactions via the end user device.

According to one embodiment, the end user device includes a clientinteraction (iXn) controller 16, vendor relationship management (VRM)module 20, and data storage device 22. The client iXn controller 16 maybe configured with logic to initiate interactions, and manage, controland/or assist a customer in the CCIM of those interactions. The clientiXn controller 16 may further be configured to communicate with thecontact center system (including the associated business and/or vendor)to exchange data to enable/facilitate the CCIM. Exemplary data that maybe exchanged is presence data of agents at the contact center.

According to one embodiment, the client iXn controller 16 is alsoequipped with capability (e.g. a tool or application) to develop controllogic for CCIM at the customer side. The control logic may include acustomized routing logic. The client iXn controller 16 may also beequipped for customer side case management, knowledge management,recording, and/or reporting.

In an exemplary use case, a customer that is identified as beingappropriate for CCIM capability may be offered to download anapplication hosting the client iXn controller 16 and/or VRM module 20 onthe end user device. According to one embodiment, the customer may belogged into the business' web site. The web site may recognize thecustomer as being a “Gold” customer, and display a prompt saying to“click here” if he wants to download the app. The customer may also beidentified as a “Gold” customer during a current interaction with acontact center agent. The agent may ask the customer if the wants todownload the app. If the answer is YES, the agent may send a link to thecustomer's end user device (e.g. as a text message, email, or the like)that the user may select to perform the download.

The application may be downloaded from an app store, from a website ofthe business, and/or the like. Once installed, the customer may beprompted to configure specific CCIM details such as, for example, acommunication protocol to use in the event that multiple protocols areavailable. According to one embodiment, an available protocol forselection may be a session-initiation protocol (SIP) conventional in theart. Other parameters to be configured may include, for example, data(e.g. information on the customer's preferred agents) that is to beshared between the end user device and the contact center system,interaction recording options, reporting options, and the like.

According to one embodiment, the customer may be prompted to identifyagents that the customer wants to monitor for presence, and/or customersthat the customer wants to add to his preferred agent list. In thisregard, the customer may be provided with a complete list of agents forthe business. The list of agents may be categorized, for example, basedon skills, departments, and the like. According to one embodiment,instead of monitoring presence of individual agents, the customer mayselect to monitor presence of an agent group. In this regard, if anymember of the group is available, the group is identified as beingavailable.

According to one embodiment, the customer may be further prompted togenerate a personalized routing script for routing interactions for thecustomer. Templates may be provided to the customer for guiding thecustomer in setting up the routing script. Default routing scripts mayalso be provided to the customer if he does not want to set up apersonalized one.

The routing script generated for the customer may be configured toreplace or plug-into the routing script utilized by the contact center.The routing script may also control timing of the interaction, targetselection (e.g. specific agents, interaction voice responseapplications, etc.), and the like. For example, the routing script maybe configured to identify an agent or agent group to which to route aninteraction. According to one embodiment, the customer's personalrouting script may be configured to prompt or await specific selectionof the agent or agent group by the customer prior to the routing of theinteraction.

In some embodiments, the routing script may automatically select apreferred agent for a particular interaction. In this regard, therouting logic may be configured to connect to the mass storage device 22to identify ratings of agents (e.g. by the customer, other customers,and the like), and select an agent identified to have, for example, thehighest rating. The rating of agents may be adjusted based on pastinteraction information provided by the customer or other third parties.

In addition to routing scripts, the client iXn controller 16 may alsoprovide a tool to develop, manage, and utilize (load) other types ofscripts. For example, dialogue scripts may be generated for guiding thecustomer during a live conversation with the contact center. Thedialogue script may automate certain steps of the conversation, such as,for example, passing personal information about the customer, greetings,and the like. Scripts may also be generated for granting to theenterprise filtered access to the customer's CCIM data.

According to one embodiment, the VRM module 20 includes logic forallowing the customer to not only be in control of customerinteractions, but also be in control of data exchanged between thecustomer and different enterprises (vendors), referred to as vendorrelationship management (VRM). In this regard, the VRM module 20 isconfigured to communicate with one or more vendor systems 28 associatedwith one or more businesses, such as, for example, the business forwhich contact center services are provided via the contact center system12, to exchange relevant data according to rules set up by the customer.According to one embodiment, the term vendor is also intended toencompass the contact center system for which contact center servicesare provided.

According to one embodiment, the VRM module 20 provides a tool to allowthe customer to control what kind of data to share, when to share, andwith which businesses to share. The tool may further allow the customerto control the type and timing of data that is received from the variousvendors with which the customer has a relationship, as is described infurther detail in U.S. application Ser. No. 14/201,738, filed on Mar. 7,2014, the content of which is incorporated herein by reference. Forexample, the customer may expose, via the VRM module 20, customeraccount information that will be needed to communicate with certainvendors. The vendors in turn may expose their availability information,such as their business hours of the contact center system 12, certaintips on communicating with the vendors, and the like.

Part of VRM may include maintaining track of interactions with thevendors, including, for example, interactions controlled by the customervia the client iXn controller, and other interactions not controlled bythe customer if CCIM is not provided for those interactions. Inaddition, the VRM module may allow the user to maintain personal notesor scores relating to the vendors and individual interactions with suchvendors. For example, the customer may provide a scoring of servicequality and of individual agents. The customer may also keep notes onhow to communicate best with a particular company (e.g. best media type,best timing, how to fast-track IVR menu, and other do's and don'ts),learned from past experience or from data shared by other customers,such as, for example, via social media. Some of the information may befed by the vendors themselves. This information may be accessed by theclient iXn controller for initiating an interaction with the vendor, orduring a CCIM session to allow the interaction to progress moreefficiently.

The client iXn controller 16 and VRM module 20 are coupled to the massstorage device 22 which may take the form of a disk drive or drive arrayconventional in the art. The mass storage device 22 may store differenttypes of records, such as, for example, interactions records, vendorrecords, configuration data, scripts, and the like. The vendor recordsmay include VRM details of different vendors with which the customer hasrelations. For example the vendor records may include, withoutlimitation, vendor metadata (e.g. contact numbers/addresses, officehours, type of business, and types of offered services), vendor profileor classification (e.g. values reflective of the vendor's speed inproviding committed service, ease of doing business with the vendor, andcorporate assessment data (e.g. risk of bankruptcy)), assessment ofagents with whom the customer has had interaction (e.g. satisfactionscores, and preference indicators), schedules of preferred agents, andoffered communication channels along with the customer's preferenceindicators for each offered channel. Each vendor record may also includedata on how to improve the customer's interaction experience with thevendor such as, for example, “tricks” to fast-track IVR dialogue (e.g. aseries of numbers to press to reach certain departments), data that isto be exposed (or not) to the vendor (e.g. last 4 digits of thecustomer's social security number which is a question that is alwaysasked during an IVR dialogue with the vendor), and other data exposed bythe vendor or collected from data shared by other customers.

According to one embodiment, the interaction records maintained in themass storage device include, without limitation, interaction metadata(e.g. time, parties, and service type), case reference where each casemay include multiple individual interactions (e.g. a case reference maybe provided to process an accident claim), business outcome (e.g. sales,or credit card offer accepted), status of interaction (e.g. case closed,finished, or not finished), and customer's annotations (e.g.satisfaction ratings or things learned from the experience).

Portions of the data stored in the mass storage device 22 may be sharedwith the vendor servers 28, contact center system 12, and/or othercustomers according to set rules. For example, agent satisfaction scoresmay be posted onto one or more social media website according to therules. The data may also be updated from these entities according to setrules.

Although throughout this discussion, the client iXn controller 16 andVRM module 20 are assumed to be separate functional units, a person ofskill in the art should recognize that the functionality of these unitsmay be combined or integrated into a single component, or furthersubdivided into further sub-units without departing from the spirit ofthe invention. According to one embodiment, the client iXn controller 16and VRM module 20 are locally hosted by the end user device as, forexample, a local application. In other embodiments, the controller andmodule may be hosted in a third party system and accessed in real-timeby the end user device as a service (e.g. over the web) during an actualCCIM session. In yet other embodiments, a hybrid solution may beprovided where the processing logic resides at the end-user device, butthe data stored in the storage device 22 is maintained in a remotecomputing environment such as, for example a cloud computingenvironment.

Referring now to the contact center system 12, the contact center systemincludes a contact center (CC) iXn controller 18 providing logic for thebusiness-side CCIM. In this regard, the CC iXn controller 18communicates with the client iXn controller for enabling CCIM ofinteractions by the customer. For example, messages may be exchanged toexpose agent presence information to the end user device. The messagesmay also be for giving control to the client iXn controller 16 forrouting an interaction initiated by the customer. In exchanging suchmessages with the end user device 10, the CC iXn controller 18 furthercommunicates with traditional CC components 24 as described in furtherdetail below.

The contact center system may be deployed in equipment of thecorresponding enterprise, a third-party service provider, and/ordeployed in a remote computing environment such as, for example, aprivate or public cloud environment with infrastructure for supportingmultiple contact centers for multiple enterprises. The variouscomponents of the contact center system may also be distributed acrossvarious geographic locations and computing environments and notnecessarily contained in a single location, computing environment, oreven computing device.

According to one embodiment, an iXn control gateway 26 may be optionallycoupled in-between the end user device 10 and contact center system 12.The iXn control gateway 26 may expose an application programminginterface (API) and/or protocols for allowing the client iXn controller16 to exchange messages with the CC iXn controller 18.

According to one embodiment, a single iXn control gateway 26 may beprovided for different contact center systems. The functionality of theclient iXn controller 16 and/or CC iXn controller 18 may reside in theiXn control gateway 26. The functionality may be accessed by bothcustomers and businesses as a service, such as, for example,software-as-a service (SaaS), as a managed service, or the like. Bothcustomers and businesses may subscribe to this service. During an actualCCIM session, data exchanged via the media and control channels may flowthrough the iXn control gateway 26, or the session may be conducteddirectly between the end user device 10 and contact center system 12 ina peer-to-peer fashion.

In embodiments where CCIM is not provided as a service, but is fullyowned and operated by the customer (e.g. CCIM application running on thecustomer's mobile device), and all business side CCIM is owned andoperated by the business directly, there may be no need for the iXncontrol gateway 26. In this embodiment, the CCIM communications betweenthe end user device 10 and contact center system 12 may be peer-to-peer.Certain components of the contact center, such as, for example, acontact center router, may also act as the iXn control gateway 26.

FIG. 2 is a more detailed block diagram of the contact center components24 according to one exemplary embodiment of the invention. According toone exemplary embodiment, the contact center system includes aswitch/media gateway 100 coupled to the communications network 14 forreceiving and transmitting calls between the customers and the contactcenter. The switch/media gateway 100 may include a telephony switchconfigured to function as a central switch for agent level routingwithin the center. In this regard, the switch 100 may include anautomatic call distributor, a private branch exchange (PBX), an IP-basedsoftware switch, and/or any other switch configured to receiveInternet-sourced calls and/or telephone network-sourced calls from acustomer, and route those calls to, for example, an agent telephonydevice. In this example, the switch/media gateway establishes a voicepath (not shown) between the calling customer and, for example, theagent telephony device.

According to one exemplary embodiment of the invention, the switch iscoupled to a call server 102 which may, for example, serve as an adapteror interface between the switch and the remainder of the routing,monitoring, and other call-handling components of the contact center.

The call server 102 may be configured to process PSTN calls, VoIP calls,and the like. For example, the call server 102 may include a sessioninitiation protocol (SIP) server for processing SIP calls. According tosome exemplary embodiments, the call server 102 may, for example,extract data about the customer interaction such as the caller'stelephone number, often known as the automatic number identification(ANI) number, or the customer's internet protocol (IP) address, or emailaddress, and communicate with other CC components and/or CC iXncontroller 18 in processing the call.

According to one exemplary embodiment of the invention, the contactcenter system 24 further includes an interactive media response (IMR)server 104, which may also be referred to as a self-help system, virtualassistant, or the like. The IMR server 104 may be similar to aninteractive voice response (IVR) server, except that the IMR server isnot restricted to voice, but may cover a variety of media channelsincluding voice. Taking voice as an example, however, the IMR server maybe configured with an IMR script for querying calling customers on theirneeds. For example, a contact center for a bank may tell callers, viathe IMR script, to “press 1” if they wish to get an account balance. Ifthis is the case, through continued interaction with the IMR, customersmay complete service without needing to speak with an agent. The IMRserver 104 may also ask an open ended question such as, for example,“How can I help you?” and the customer may speak or otherwise enter areason for contacting the contact center.

The routing server 106 may be configured to take appropriate action forprocessing the call. For example, for non-CCIM interactions, the routingserver 106 may use data about the call to determine how the call shouldbe routed. If the call is to be routed to a contact center agent, therouting server 106 may select an agent for routing the call based, forexample, on a routing strategy employed by the routing server 106, andfurther based on information about agent availability, skills, and otherrouting parameters provided, for example, by a statistics server 108.For CCIM interactions, the routing server 106 may pass control of therouting to the client iXn controller 16, or receive instructions fromthe client iXn controller to route the call.

In some embodiments, the routing server 106 may query a customerdatabase, which stores information about existing clients, such ascontact information, service level agreement (SLA) requirements, natureof previous customer contacts and actions taken by contact center toresolve any customer issues, and the like. The database may be managedby any database management system conventional in the art, such asOracle, IBM DB2, Microsoft SQL server, Microsoft Access, PostgreSQL,MySQL, FoxPro, and SQLite, and may be stored in a mass storage device110. The routing server 106 may query the customer information from thecustomer database via an ANI or any other information collected by theIMR 104.

According to one embodiment the statistics server 108 or a separatepresent server may be configured to provide agent availabilityinformation to all subscribing clients. Such clients may include, forexample, the routing server 106, CC iXn controller 18, and/or client iXncontroller 16.

Upon identification of an agent to whom to route the call, a connectionis made between the caller and an agent device 112 a-112 c (collectivelyreferenced as 112) of the identified agent. Received information aboutthe caller and/or the caller's historical information may also beprovided to the agent device for aiding the agent in better servicingthe call. In this regard, each agent device 112 may include a telephoneadapted for regular telephone calls, VoIP calls, and the like. The agentdevice 112 may also include a computer for communicating with one ormore servers of the contact center and performing data processingassociated with contact center operations, and for interfacing withcustomers via voice and other multimedia communication mechanisms.

The contact center may also include a reporting server 114 configured togenerate reports from data aggregated by the statistics server 108. Suchreports may include near real-time reports or historical reportsconcerning the state of resources, such as, for example, average waitingtime, abandonment rate, agent occupancy, and the like. The reports maybe generated automatically or in response to specific requests from arequestor (e.g. agent/administrator, contact center application, and/orthe like).

The contact center may also include a multimedia/social media server 116for engaging in media interactions other than voice interactions withthe end user devices 10 and/or web servers 118. The media interactionsmay be related, for example, to email, vmail (voice mail through email),chat, video, text-messaging, web, social media, co-browsing, and thelike. The web servers 118 may include, for example, social interactionsite hosts for a variety of known social interaction sites to which anend user may subscribe, such as, for example, Facebook, Twitter, and thelike. The web servers may also provide web pages for the enterprise thatis being supported by the contact center. End users may browse the webpages and get information about the enterprise's products and services.The web pages may also provide a mechanism for contacting the contactcenter, via, for example, web chat, voice call, email, web real timecommunication (WebRTC), or the like.

According to one exemplary embodiment of the invention, in addition toreal-time interactions, deferrable (also referred to as back-office oroffline) interactions/activities may also be routed to the contactcenter agents. Such deferrable activities may include, for example,responding to emails, responding to letters, attending trainingseminars, or any other activity that does not entail real timecommunication with a customer. In this regard, an iXn server 122interacts with the routing server 106 for selecting an appropriate agentto handle the activity. Once assigned to an agent, the activity may bepushed to the agent, or may appear in the agent's workbin 120 a-120 c(collectively referenced as 120) as a task to be completed by the agent.The agent's workbin may be implemented via any data structureconventional in the art, such as, for example, a linked list, array,and/or the like. The workbin may be maintained, for example, in buffermemory of each agent device 112. According to one embodiment deferrableinteractions may also be subject to CCIM.

According to one exemplary embodiment of the invention, the mass storagedevice(s) 110 may store one or more databases relating to agent data(e.g. agent profiles, schedules, etc.), customer data (e.g. customerprofiles), interaction data (e.g. details of each interaction with acustomer, including reason for the interaction, disposition data, timeon hold, handle time, etc.), and the like. According to one embodiment,some of the data (e.g. customer profile data) may be maintained in acustomer relations management (CRM) database hosted in the mass storagedevice 110 or elsewhere. The mass storage device may take form of a harddisk or disk array as is conventional in the art.

The contact center may also include a reporting server 114 configured togenerate reports from data aggregated by the statistics server 108. Suchreports may include near real-time reports or historical reportsconcerning the state of resources, such as, for example, average waitingtime, abandonment rate, agent occupancy, and the like. The reports maybe generated automatically or in response to specific requests from arequestor (e.g. agent/administrator, contact center application, and/orthe like).

The various servers of FIG. 2 may each include one or more processorsexecuting computer program instructions and interacting with othersystem components for performing the various functionalities describedherein. The computer program instructions are stored in a memoryimplemented using a standard memory device, such as, for example, arandom access memory (RAM). The computer program instructions may alsobe stored in other non-transitory computer readable media such as, forexample, a CD-ROM, flash drive, or the like. Also, although thefunctionality of each of the servers is described as being provided bythe particular server, a person of skill in the art should recognizethat the functionality of various servers may be combined or integratedinto a single server, or the functionality of a particular server may bedistributed across one or more other servers without departing from thescope of the embodiments of the present invention. In addition, thefunctionality the functionality of the CC iXn controller 18 may beincorporated into one or more of the CC components 24 or vice versa aswill be apparent to a person of skill in the art.

In the various embodiments, the term interaction is used generally torefer to any real-time and non-real time interaction that uses anycommunication channel including, without limitation telephony calls(PSTN or VoIP calls), emails, vmails (voice mail through email), video,chat, screen-sharing, text messages, social media messages, webreal-time communication (e.g. WebRTC calls), and the like.

FIG. 3 is a more detailed block diagram of a client iXn controller 16 aand a CC iXn controller 18 a according to one embodiment of theinvention Like reference number in this and other figures of theapplication reference like components. For example, client iXncontroller 16 a may be similar to client iXn controller 16, and CC iXncontroller 18 a may be similar to CC iXn controller 18. In theembodiment of FIG. 3, the CC iXn controller 18 a provides CCIMcapability to the client iXn controller 16 a as a web service over thecommunications network 14. Any web protocol conventional in the art maybe used for the web communication, such as, for example, SOAP and/orHTTP.

The CC iXn controller 18 a may include a routing server 106 a which maybe similar to the routing server 106 of FIG. 2. The CC routing server106 a is coupled to a CC statistics server 108 a and a CC telephonyserver 240 a which may be similar to the statistics server 108 and callserver 240 of FIG. 2.

According to one embodiment, the client iXn controller 16 a includes aclient router 200 a and client iXn media controller 202. The clientrouter 200 a may be configured as a “lite” version of the CC routingserver 106 a, and the client iXn media controller 202 may be configuredas a “lite” version of the CC telephony server 240 a. In this regard,the client router 200 a and iXn media controller 202 a providefunctionality similar to the basic functionality provided respectivelyby the CC routing server 106 a and telephony server 240 a.

According to one embodiment, the client iXn controller 16 a may beconfigured to monitor the presence of monitored agents (e.g. agents in acustomer's preferred agent list). This may be done, for example, by theclient router 200 a requesting status of one or more of the monitoredagents, either periodically or on an as-needed basis. The CC iXncontroller 18 a receives the request, and invokes the CC routing server106 a to in turn query the statistics server 108 a for statusinformation of the one or more agents. The agent status information fora particular agent may indicate, for example, whether the agent isavailable, the communication medium for which the agent is agent, andthe like. The retrieved agent status information is forwarded to theclient router 200 a over the communication network 14.

According to one embodiment, the routing logic for routing interactionsinvolving the customer resides in the client iXn controller. In thisregard, the client router 200 a and/or iXn media controller 202 acommunicates with the CC routing server 106 a to request that aninteraction be routed to an agent or agent group as instructed by thecustomer's routing logic. Such agent may be selected automatically bythe customer's routing logic based on, for example, agents that havebeen identified by the customer as being preferred, and currentavailability of such agents. The routing request may include data of therequesting user (e.g. a customer phone number), and identification ofthe desired agent or agent group. The CC routing server 106 a theninteracts with the CC telephony server 240 a to cause the interaction tobe routed to the agent device of the selected agent.

FIG. 4 is a more detailed block diagram of a client iXn controller 16 band a CC iXn controller 18 b according to one embodiment of theinvention. In the embodiment of FIG. 4, SIP is used for exchanginginteraction data between the client iXn controller 16 b and CC iXncontroller 18 b. In this regard, the CC iXn controller includes a SIPserver 256 a which may be similar to the call server 102 of FIG. 2.

The client iXn controller 16 b is equipped with a client router 200 b,client SIP server 250 a, and client statistics server 252 a, which maybe “lite” versions of respectively the routing server 106, CC SIP server256 a, and the contact center CC statistics server 108.

According to one embodiment, the client statistics server 252 a may beconfigured to exchange messages with a contact center presence server254 using SIMPLE (SIP for Instant Messaging and Presence LeveragingExtensions) to detect presence of desired agents. According to oneembodiment, the contact center presence server may be in communicationwith, or incorporated into, the contact center statistics server, toprovide status of the identified agents. Once received, the clientstatistics server 252 a may expose the agent status data to the clientrouter 200 b for selecting an agent or agent group with which tocommunicate. The agent status data may also be provided for display bythe CCIM application to allow a customer to manually select the agentwith whom he wants to communicate.

According to one embodiment, the client router 200 b invokes the clientSIP server 250 a to exchange SIP messages with the CC SIP server 256 ato cause routing of an interaction from/to the end user device to aparticular agent or agent group. Data about the end-user as well as therequested agent or agent group may be transmitted via the SIP messages.The CC SIP server 256 a then interacts with one or more CC components tocause the interaction to be routed to the agent device of the selectedagent.

FIG. 5 is a more detailed block diagram of a client iXn controller 16 cand a CC iXn controller 18 c according to one embodiment of theinvention. In the embodiment of FIG. 5, a proprietary protocol is usedfor exchanging messages between the client iXn controller 16 c and CCiXn controller 18 c. In this regard, the CC iXn controller 18 c includesa CC routing server 106 c which may be similar to the routing server 106of FIG. 2, for exchanging messages via the proprietary protocol. Thecontact center system 12 c also includes a CC telephony server 240 b anda CC statistics server 108 b which may be similar, respectively, to thecall server 102 and statistics server 108 of FIG. 2.

The client iXn controller 16 c is equipped with a client router 200 c,client telephony server 280 a, and client statistics server 252 b, whichmay be “lite” versions of respectively the CC routing server 106 c, CCtelephony server 240 b, and CC statistics server 108 b.

According to one embodiment, the client statistics server 252 b may beconfigured to request and receive agent status information from the CCstatistics server 108 b using the proprietary protocol. In this regard,the client statistics server 252 b subscribes to the CC statisticsserver 108 b to receive agent status information as would any otherclient located at the contact center (e.g. the CC routing server 106 c).Once subscribed, the client statistics server 252 b exposes the agentstatus data to its subscribing clients, such as, for example, the clienttelephony server 208 a and client router 200 c.

According to one embodiment, the client telephony server 280 a invokesthe client router 200 c to exchange messages with the CC routing server106 c to cause routing of an interaction to a particular agent or agentgroup. Data about the end-user as well as the requested agent or agentgroup may be transmitted via the proprietary protocol. The contactcenter telephony server 240 b then allows the end user device toestablish connection with the available agent device.

FIG. 6 is a more detailed block diagram of a client iXn controller 16 dand a CC iXn controller 18 d according to one embodiment of theinvention. In the embodiment of FIG. 6, federation principles are usedfor exchanging messages between the client iXn controller 16 d and CCiXn controller 18 d. In this regard, the CC iXn controller 18 d includesa CC federation proxy 292 that acts as an intermediary for receivinginteraction data from the client iXn controller 16 d. As in a typicalfederated environment, the federation proxy 292 may be configured toauthenticate requests from the client iXn controller and give access tocertain services and data based on the authentication. The contactcenter system 12 d also includes a CC telephony server 240 c and a CCstatistics server 108 c which may be similar, respectively, to the callserver 102 and statistics server 108 of FIG. 2.

According to one embodiment, the client iXn controller 16 c is alsoequipped with a federation proxy 290 for transmitting interactionrouting requests to the CC iXn controller 18 d. The client iXncontroller 16 d may further include an iXn media controller 202 b,client router 200 d, and client statistics server 252 c, which may be“lite” versions of respectively the CC telephony server 240 c, routingserver 106, and CC statistics server 108 c.

According to one embodiment, the client statistics server 252 c may beconfigured to request and receive agent status information from the CCstatistics server 108 c after the customer has been authenticated by theCC federation proxy 292. In this regard, the client statistics server252 c subscribes to the CC statistics server 108 c to receive agentstatus information as would any other client located at the contactcenter (e.g. the CC telephony server 240 c). Once subscribed, the clientstatistics server 252 c exposes the agent status data to its subscribingclients, such as, for example, the iXn media controller 202 b and clientrouter 200 d.

According to one embodiment, the iXn media controller 202 b invokes theclient router 200 d to transmit requests to cause routing of aninteraction to a particular agent or agent group. Data about theend-user as well as the requested agent or agent group may betransmitted in the request. According to one embodiment, the request isforwarded to the CC iXn controller 18 d via the client federation proxy290.

As a person of skill in the art should appreciate, for interactionsother than voice interactions, the telephony/SIP servers at the customerand client side are replaced with a CC or client interaction serversimilar to the interaction server 122 of FIG. 2 which is configured toprocess non-voice interactions.

FIG. 7 is a flow diagram of a process executed by the client iXncontroller 16 to allow CCIM for a customer according to one embodimentof the invention. The process may start in response to a customerinvoking or launching the CCIM application hosting the client iXncontroller 16. The application may be dedicated to a single business(e.g. Bank of America), a class of businesses (all banks used by thecustomer), and/or the like. The customer may launch the application toinitiate contact with a particular business. According to oneembodiment, in response to the customer invoking the application, theapplication determines, in act 300, whether any unresolved interactionsexist for the customer. If the answer is YES, the unresolved interactionis resumed in act 302. For simplicity purposes, this step is generallyidentified as a single block 302. Of course, the resuming of theunresolved interaction may involve execution of one or more of the actsidentified in FIG. 7.

According to one embodiment, determination as to whether an unresolvedinteraction exists is performed by searching the mass storage device 22for interaction records stored for the customer that have beenidentified as being unresolved. Such records may further indicate therouting strategy that was invoked, and the portion of the routingstrategy that was executed when the interaction was left uncompleted.The application may be configured to resume the interaction from thispoint on. For example, a next step in the routing strategy may be toselect an agent with the right skills to handle the interaction.

The resumed interaction may utilize the same or different communicationchannels that were used during the last interaction. For example, thecustomer may have started a flight booking process on the web page ofthe business when the interaction was discontinued. The customer may beable to resume the interaction by invoking the application and placing acall to his preferred agent. Of course, the application may beconfigured to inquire whether the customer wants to resume thisinteraction before doing so.

If there are no unresolved interactions to be resumed, the applicationwaits and detects a condition to initiate an interaction to anidentified agent or agent group. The condition may be, for example,receipt of a customer command to initiate the interaction. For example,the application may provide a graphical user interface withavailability/presence information of preferred agents and/or agentgroups, along with an option to “call,” “email,” or “chat” with suchagents. Selection of one of the interaction options initiates thecorresponding interaction with the identified agent or agent group. Thepresence information may indicate whether the agent is busy with anotherinteraction, not scheduled for work, and/or the like. According to oneembodiment, the list of preferred agents and agent groups isconfigurable and modifiable by the customer at any time. For example,the graphical user interface may provide options to add, delete, ormodify agents or agent groups from the customer's preferred list.

In one embodiment, detecting a particular event may automaticallytrigger the interaction, or display a question to the user as to whetherhe wants to initiate the interaction. The events may be, for example,detecting a particular time (e.g. if the user has set a timer toinitiate the interaction), or detecting a monitored condition (e.g. ifcharge on a credit card was above a preset amount). In another example,even if the user manually indicates that he wants to initiate theinteraction, the application may detect a conflict and either block thecall, or display the conflict and ask the user to confirm that he wantsto proceed with the interaction. For example, the application may haveaccess to a preconfigured rule (e.g. set by the customer) that no callsare to be initiated when the customer is driving (e.g. when theBluetooth device in the car is active). In another example, theapplication may have access to the customer's calendar and detect thatthe customer is scheduled to have a meeting that would overlap with theinteraction.

For purposes of describing the embodiment of FIGS. 7 and 8, it isassumed that the customer has selected a telephony interaction byselecting the “call” option, and no conflicts have been detected toallow the interaction. According to one embodiment, although a specificagent or agent group is listed next to the call option, the number thatis called may be a general telephone number of the contact center.

In another embodiment, the customer simply transmits a “call” command,and the routing logic at the customer end selects an agent according to,for example, preference settings, user ratings, and the like.

According to one embodiment, if the customer selects an agent whosestatus information indicates that he is not available to handle thecall, the application may respond by asking the customer if he or shewants to try connecting anyway, or whether he or she wants to try laterwhen the agent's presence status indicates that he is available. If thecustomer indicates that he or she wants to try later, the applicationmay be configured to monitor the identified agent's presenceinformation, and once the agent is indicated to be present,automatically launch the interaction with the identified agent. Ofcourse, a prompt may be displayed to the customer to confirm that theinteraction is still desired. For example, the prompt may say, “Agent Xis now available, please click to connect.” Prior to sending the prompt,the contact center system may reserve the agent for a configurable shorttime (e.g. 5 seconds) to allow the customer to react. If that agent isdesired by more than one customer, the first customer who reacts (e.g.clicks to connect) gets the connection to the agent. Once the connectionis established, a negative alert may be sent by the contact centersystem to the other customers indicating that the agent is no longeravailable, and asking if they want to be notified again. According toone embodiment, the customers who originally got the positive alert ofthe agent availability get the negative alert if the connection cannotbe established for those customers despite their clicking to connect.

If the call is to proceed despite the agent being unavailable, theclient iXn controller 16 transmits an agent reservation request in act306 to the CC iXn controller 18 to reserve the selected agent or agentgroup. According to one embodiment, the request is transmitted to the CCiXn controller 18 over the data channel prior to or concurrently withthe transmitting of call data. According to one embodiment, thereservation request is received at a central place at the contact centerwhere logic for agent reservation resides, such as, for example, at a CCtelephony server 240. If the reservation request identifies an agentgroup or a list with various possible agents, the CC telephony server240 may be configured to select (e.g. randomly) one of the variousagents of the group or list for reservation.

Once an agent is reserved for the particular interaction, the agent isblocked for any other interactions for a particular period of time (e.g.15 seconds). For example, the agent may be identified by the statisticsserver 108 as being in a busy/unavailable state. It is possible thatmultiple agent reservation requests for the same agent may beconcurrently received from multiple routing servers (e.g. client routers200 or CC routing servers 105). In this case, priority data associatedwith the requests may be used for determining to whom to assign theagent. Priority determinations may be made based on, for example,customer segmentation information about the customer associated with theinteraction. According to this example, requests relating to “Gold”customers may be given higher priority than requests relating to“Bronze” customers.

In act 308, a determination is made as to whether the agent reservationwas successful. If the answer is NO, another agent reservation requestis transmitted to either the same agent or agent group, or to a newagent or agent group. In this regard, the routing logic at the clientrouter 200 determines whether to retry the same agent/agent group, orselect a next preferred agent or agent group. Identification of the nextpreferred agent or agent group may be pre-configured by the customer.The customer may also manually select a different agent or agent groupin response to indication of the unsuccessful agent reservation request.Of course, instead of the agent selecting a specific agent, freedom maybe given to the enterprise to select an available agent as would be doneaccording to conventional routing mechanisms.

If an agent was successfully reserved, the client iXn controller 16, inact 310, transmits a call control message to the CC iXn controller 18over the data channel. According to one embodiment, the telephony server240 coupled to the switch/media gateway 100 that receives the voice callvia the voice channel, receives the call control message via the datachannel. The call control message may contain, for example, data aboutthe interaction, customer, and/or reserved agent. According to oneembodiment, the client iXn controller 16 further provides a dialerapplication for launching the actual voice call towards the contactcenter. In this regard, the dialer application functions as a switch forthe end user device.

Once launched, the voice call lands on the switch/media gateway 100 atthe contact center until routed to an appropriate destination. Asdescribed in further detail in FIG. 8, when the call arrives at theswitch/media gateway 100, the CC telephony server 240 determines arouting point (also referred to an external route point) to which thecall should be transferred based on the received interaction data.According to one embodiment, the identified routing point is a personalrouting point that is enabled for CCIM.

In act 312, the client iXn controller 16 (e.g. client telephony server280) receives a call transfer message from the CC iXn controller 18 thatidentifies the transfer routing point, along with any interaction datacollected by the CC iXn controller. By forwarding the collectedinteraction data from the CC iXn controller 18 to the client iXncontroller 16, data, such as identification of the reserved agent, ispreserved.

According to one embodiment, the transfer routing point is associatedwith the client telephony server 280 hosted by the client iXn controller16. The call transfer message is received by the client telephony server280 over the data channel. The actual call is also received by thedialer application that acts as the switch for the end user device. Inresponse to the call arriving at the dialer application, the clienttelephony server 280 informs the client router 200 of the call.

In act 316, the client router proceeds to route the call according toits routing logic. In this regard, the routing logic may be configuredto identify the preferred agent that has been reserved for theinteraction (e.g. based on the received interaction data), and proceedto route the call to the reserved agent. The routing logic mayoptionally check whether the reserved agent is indeed still available.In routing the call, the client router 200 invokes the dialerapplication to call the access (directory) number of the reserved agent.The access number may be provided in the call transfer message from theCC iXn controller transmitted in act 310. A voice connection is thenmade with the customer and the reserved agent.

FIG. 8 is a flow diagram of a process executed by the CC iXn controller18 to allow CCIM for a customer according to one embodiment of theinvention. According to one embodiment, the process starts, and the CCiXn controller receives, in act 400, the call control message containinginteraction data from the client iXn controller 16 over the datachannel.

In act 402, the CC telephony server 240 identifies an external routepoint based on the received interaction data. For example, the CCtelephony server 240 may identify the caller number in the interactiondata as one that is enabled for CCIM. A personal route point is thusidentified and reserved for routing the call. The interaction datareceived from the client iXn controller is then saved in associationwith the personal route point. According to one embodiment, the personalroute point is associated with a directory number of the dialerapplication hosted by the client iXn controller 16.

In act 404, the actual voice call launched by the end user device isreceived at the switch/media gateway 100, and the call is matched to thedata saved in association with the personal route point.

In act 406, the CC telephony server 240 transfers the call to thepersonal route point. The transfer of the call further causes transferof the interaction data to the client telephony server 280. According toone embodiment, transfer of the call to the client telephony serverrelinquishes control of the call by the contact center. Thus, furtherrouting of the call to the reserved agent is performed based on routinglogic controlled by the customer instead of routing logic under thecontrol of the contact center.

Although routing is used herein as a main example of interactionprocessing by the customer, a person of skill in the art shouldrecognize that the customer may be in control of other aspects ofinteraction processing, such as, for example, obtaining interactionhistory data, checking status of interactions, and the like. Also,although the examples of customer controlled interactions providedherein relate to inbound real-time interactions initiated by thecustomer (e.g. voice calls, chat, directly routed emails, etc.), aperson of skill in the art should recognize that deferrable interactionscould also be controlled by the customer, such as, for example, emailsthat are placed in the agent's workbin for handling as time permits.Outbound interactions initiated by the contact center may also becontrolled by the customer, such as, for example, by enabling thecustomer to control the customer's entries in calling lists by removingthe customers number, changing the time of the outbound contact,selecting a telephone number, assigning the outbound interaction tocertain agents, and the like.

In addition to embodiments where control of the interaction is by thecustomer, a hybrid solution is also contemplated where certain parts ofthe interaction processing are controlled by the customer, and otherparts are controlled by the business. For example, certain internalprocesses for claim approval will stay under business control while thecustomer may control the claim adjuster who ultimately handles theclaim.

In another embodiment, a “soft” CCIM may be provided to a customer wherethe customer merely expresses interaction intent and preferred agent(s),but the actual final assignment of the interaction to an agent is doneby the business that tries to accommodate the customer's preference.

Social Media Integrated Agent Routing

According to one embodiment, a customer may share personal ranking,recommendation, and/or satisfaction information (collectively referredto as “rating”) about agents, services, and/or products, with otherusers. The agent ratings may be indicative of qualifications of theagents, customer satisfaction provided by the agents, and/or the like.According to one embodiment, the VMR module 20 may be invoked to collectand share the rating information on social media sites such as Facebookand Twitter. The information may also be shared on rating websites suchas Yelp. According to one embodiment, the CCIM application provides agraphical user interface to prompt a user to rate an agent (e.g. afteran interaction with such agent).

According to one embodiment, the client CC iXn controller 16 and/or VRMmodule 20 may be configured to automatically monitor websites on theInternet for ratings of agents of a particular contact center that areposted by other customers. For example, ratings may be obtained for allagents listed in the customer's preferred agent list, and an average ofsuch ratings may be displayed by the CCIM application along with anypersonal rating provided by the customer. The collected ratings for anagent may be used to propose the agent to a preferred status, or demotethe agent to a less preferred status. The rating information may also beused to select an agent to whom to route an interaction enabled forCCIM, if no manual selection was made by the customer.

According to one embodiment, the exposing of agent rating information inaddition to agent presence information allows the customer to have amore complete set of data for deciding when and with which agent to havea CCIM enabled interaction. For example, if a first agent with a lowrating is identified as being available for a voice interaction, but asecond agent with a higher rating is identified as being busy for suchvoice interaction, the customer may want to wait until agent two becomesavailable prior to initiating the call.

Agent rating and presence information may also be used for non-CCIMenabled interactions. FIGS. 9A-9B are exemplary signaling diagrams ofmessages exchanged between an end user and the contact center system ina non-CCIM enabled interaction according to one embodiment of theinvention. According to the embodiment of FIGS. 9A-9B, the end userdevice 10 may host an application that allows interaction with thecontact center system 12 to gather information about agents, products,and services of the contact center.

In act 404, the end user device 10 invokes the application and submits amessage to the contact center system 12 indicating that the customer hasa problem that needs to be solved. For example, the customer may selectan “I have a problem” button displayed by the application.

In act 406, the contact center system (e.g. multimedia/social mediaserver 116) receives the data, and in response, transmits a secondmessage to the application for gathering information on the cause of theproblem. For example, the customer may be prompted to enter the name ofthe product to which the problem is related. In another embodiment, thehistory of interactions with the application may provide clue as to theproduct or service that is causing problems for the customer.

In act 408, the application transmits details on the problem, such as,for example, the product name. In the example of FIGS. 9A-9B, thecustomer identifies that the problem is product related, and the productname is “Vacuum 502.”

In response to identifying the product causing problems, the contactcenter system may be configured, in act 410, to retrieve productmetadata including, for example, available services relating to theproduct, agent skills required to deal with issues with the product, andthe like. Such information may be retrieved, for example, from the massstorage device 100 located at the contact center system 12.

Based on the retrieved product metadata, suggestions are provided to thecustomer, in act 412 as to how to resolve the issue. The options mayinclude self-help options as well as interaction options with liveagents that have been identified as having skills for handling theinteraction. According to one embodiment, the contact center system 12exposes agent presence information to the application for each type ofinteraction channel. In the example of FIGS. 9A-9B, agent 1 and agent 2have skills to have a chat about the identified product/issue, whileagent 2 has skills to conduct a voice conversation about the identifiedproduct/issue. Agent 1 is identified as being available for chat, whileagent 2 is busy. Agent 2 is identified as being busy for voiceinteractions.

According to one embodiment, in response to identification of agentswith skills for handling the particular issue, the application at theend user device 10 may be configured to search, in act 414, one or moresocial networks for ratings by other people on the product and/or agentsidentified by the contact center system 12. For example, the applicationmay be configured to go inquire social networks like Facebook to see isany of the customer's friends have provided a rating for the product oragents (e.g. a total number of “likes” or “dislikes” for a particularagent). If such information is available, the agent rating informationis returned to the application in act 416 for display to the customer.Embodiments of the present invention thus provide the customer fullinformation as to agent availability as well as agent ratings forhelping the customer decide how he wants to interact with the contactcenter.

According to one embodiment, the customer may configure the applicationto automatically select the agent with the highest rating if the agentis available. If the highest rated agent is not available, theapplication may be configured to prompt the customer to indicate how hewould like to proceed. For example, the customer may want to proceedwith a lower rated agent that is currently available, wait for thehigher rated agent, or the like.

In the example of FIG. 9, the end user device 10 transmits, in act 418,a message to the contact center system 12 indicating that the customerwill wait for agent 2. In response, the contact center system (e.g. callserver 102) creates a virtual interaction in act 420 where the target ofthe interaction is set to agent 2. The contact center system 12 furthertransmits a message, in act 422, that the customer will be notified whenagent 2 becomes available.

When agent 2 does become available, the contact center system 12reserves agent 2 in act 424 and pushes notification to the customer inact 426 as to this fact. The customer is also provided information onthe choices that he can take, such as receiving the number of agent 2,requesting that agent 2 call the customer at his number, or requestingadditional time before engaging in the interaction with agent 2.

If the customer needs additional time, the contact center systemreleases agent 2, re-reserves him, and inquires the customer as towhether he wants to engage in the interaction (collectively referencedas acts 428 and 430), until the customer indicates, in act 432, that hewants the access telephone number of agent 2 to initiate theinteraction. In response, the contact center system 12 allocates thenumber and associates it to the customer.

In acts referred generally as 436, the customer dials the telephonenumber for agent 2, and the contact center system 12 matches theincoming call to the stored customer data and routes the call to anagent device for agent 2 400.

Once the call between the customer and the agent terminates, the contactcenter system 12 may transmit a survey to get feedback on theexperience. The customer may respond or decline the survey. Even if thecustomer declines, he or she may be willing to share his experience withhis friends. In this regard, the application or VRM module 20 mayprovide a graphical user interface to allow the customer to captureinformation about the experience. Such information may include, forexample, a rating given to the agent based on the experience. Theinformation is stored in the customer's mass storage device 22 but maybe exposed, in act 438, to one or more businesses, social medianetworks, and the like, based on settings configured by the customer.For example, the VRM module 20 may access APIs exposed by various socialnetworks to automatically post the experience information on thosenetworks.

Although the interaction in FIGS. 9A-9B are described as non-CCIMenabled interaction, a person of skill in the art should recognize thatthe interaction may also be a CCIM enabled interaction where the routinglogic that is executed to route the interaction is controlled by thecustomer instead of the contact center. In this regard, when the ratingsof the first and second agents are received in act 416, the CCIMapplication may be configured to, either automatically or in response toa user command, request an interaction specifying the higher ratedagent, employing a process similar to the process described with respectto FIGS. 7 and 8.

Each of the various servers, controllers, switches, gateways, engines,and/or modules (collectively referred to as servers) in theafore-described figures may be a process or thread, running on one ormore processors, in one or more computing devices 1500 (e.g., FIG. 10A,FIG. 10B), executing computer program instructions and interacting withother system components for performing the various functionalitiesdescribed herein. The computer program instructions are stored in amemory which may be implemented in a computing device using a standardmemory device, such as, for example, a random access memory (RAM). Thecomputer program instructions may also be stored in other non-transitorycomputer readable media such as, for example, a CD-ROM, flash drive, orthe like. Also, a person of skill in the art should recognize that acomputing device may be implemented via firmware (e.g. anapplication-specific integrated circuit), hardware, or a combination ofsoftware, firmware, and hardware. A person of skill in the art shouldalso recognize that the functionality of various computing devices maybe combined or integrated into a single computing device, or thefunctionality of a particular computing device may be distributed acrossone or more other computing devices without departing from the scope ofthe exemplary embodiments of the present invention. A server may be asoftware module, which may also simply be referred to as a module. Theset of modules in the contact center may include servers, and othermodules.

The various servers may be located on a computing device on-site at thesame physical location as the agents of the contact center or may belocated off-site (or in the cloud) in a geographically differentlocation, e.g., in a remote data center, connected to the contact centervia a network such as the Internet. In addition, some of the servers maybe located in a computing device on-site at the contact center whileothers may be located in a computing device off-site, or serversproviding redundant functionality may be provided both via on-site andoff-site computing devices to provide greater fault tolerance. In someembodiments of the present invention, functionality provided by serverslocated on computing devices off-site may be accessed and provided overa virtual private network (VPN) as if such servers were on-site, or thefunctionality may be provided using a software as a service (SaaS) toprovide functionality over the internet using various protocols, such asby exchanging data using encoded in extensible markup language (XML) orJavaScript Object notation (JSON).

FIG. 10A and FIG. 10B depict block diagrams of a computing device 1500as may be employed in exemplary embodiments of the present invention.Each computing device 1500 includes a central processing unit 1521 and amain memory unit 1522. As shown in FIG. 10A, the computing device 1500may also include a storage device 1528, a removable media interface1516, a network interface 1518, an input/output (I/O) controller 1523,one or more display devices 1530 c, a keyboard 1530 a and a pointingdevice 1530 b, such as a mouse. The storage device 1528 may include,without limitation, storage for an operating system and software. Asshown in FIG. 10B, each computing device 1500 may also includeadditional optional elements, such as a memory port 1503, a bridge 1570,one or more additional input/output devices 1530 d, 1530 e and a cachememory 1540 in communication with the central processing unit 1521. Theinput/output devices 1530 a, 1530 b, 1530 d, and 1530 e may collectivelybe referred to herein using reference numeral 1530.

The central processing unit 1521 is any logic circuitry that responds toand processes instructions fetched from the main memory unit 1522. Itmay be implemented, for example, in an integrated circuit, in the formof a microprocessor, microcontroller, or graphics processing unit (GPU),or in a field-programmable gate array (FPGA) or application-specificintegrated circuit (ASIC). The main memory unit 1522 may be one or morememory chips capable of storing data and allowing any storage locationto be directly accessed by the central processing unit 1521. As shown inFIG. 10A, the central processing unit 1521 communicates with the mainmemory 1522 via a system bus 1550. As shown in FIG. 10B, the centralprocessing unit 1521 may also communicate directly with the main memory1522 via a memory port 1503.

FIG. 10B depicts an embodiment in which the central processing unit 1521communicates directly with cache memory 1540 via a secondary bus,sometimes referred to as a backside bus. In other embodiments, thecentral processing unit 1521 communicates with the cache memory 1540using the system bus 1550. The cache memory 1540 typically has a fasterresponse time than main memory 1522. As shown in FIG. 10A, the centralprocessing unit 1521 communicates with various I/O devices 1530 via thelocal system bus 1550. Various buses may be used as the local system bus1550, including a Video Electronics Standards Association (VESA) Localbus (VLB), an Industry Standard Architecture (ISA) bus, an ExtendedIndustry Standard Architecture (EISA) bus, a MicroChannel Architecture(MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI Extended(PCI-X) bus, a PCI-Express bus, or a NuBus. For embodiments in which anI/O device is a display device 1530 c, the central processing unit 1521may communicate with the display device 1530 c through an AdvancedGraphics Port (AGP). FIG. 10B depicts an embodiment of a computer 1500in which the central processing unit 1521 communicates directly with I/Odevice 1530 e. FIG. 10B also depicts an embodiment in which local bussesand direct communication are mixed: the central processing unit 1521communicates with I/O device 1530 d using a local system bus 1550 whilecommunicating with I/O device 1530 e directly.

A wide variety of I/O devices 1530 may be present in the computingdevice 1500. Input devices include one or more keyboards 1530 a, mice,trackpads, trackballs, microphones, and drawing tablets. Output devicesinclude video display devices 1530 c, speakers, and printers. An I/Ocontroller 1523, as shown in FIG. 10A, may control the I/O devices. TheI/O controller may control one or more I/O devices such as a keyboard1530 a and a pointing device 1530 b, e.g., a mouse or optical pen.

Referring again to FIG. 10A, the computing device 1500 may support oneor more removable media interfaces 1516, such as a floppy disk drive, aCD-ROM drive, a DVD-ROM drive, tape drives of various formats, a USBport, a Secure Digital or COMPACT FLASH™ memory card port, or any otherdevice suitable for reading data from read-only media, or for readingdata from, or writing data to, read-write media. An I/O device 1530 maybe a bridge between the system bus 1550 and a removable media interface1516.

The removable media interface 1516 may for example be used forinstalling software and programs. The computing device 1500 may furthercomprise a storage device 1528, such as one or more hard disk drives orhard disk drive arrays, for storing an operating system and otherrelated software, and for storing application software programs.Optionally, a removable media interface 1516 may also be used as thestorage device. For example, the operating system and the software maybe run from a bootable medium, for example, a bootable CD.

In some embodiments, the computing device 1500 may comprise or beconnected to multiple display devices 1530 c, which each may be of thesame or different type and/or form. As such, any of the I/O devices 1530and/or the I/O controller 1523 may comprise any type and/or form ofsuitable hardware, software, or combination of hardware and software tosupport, enable or provide for the connection to, and use of, multipledisplay devices 1530 c by the computing device 1500. For example, thecomputing device 1500 may include any type and/or form of video adapter,video card, driver, and/or library to interface, communicate, connect orotherwise use the display devices 1530 c. In one embodiment, a videoadapter may comprise multiple connectors to interface to multipledisplay devices 1530 c. In other embodiments, the computing device 1500may include multiple video adapters, with each video adapter connectedto one or more of the display devices 1530 c. In some embodiments, anyportion of the operating system of the computing device 1500 may beconfigured for using multiple display devices 1530 c. In otherembodiments, one or more of the display devices 1530 c may be providedby one or more other computing devices, connected, for example, to thecomputing device 1500 via a network. These embodiments may include anytype of software designed and constructed to use the display device ofanother computing device as a second display device 1530 c for thecomputing device 1500. One of ordinary skill in the art will recognizeand appreciate the various ways and embodiments that a computing device1500 may be configured to have multiple display devices 1530 c.

A computing device 1500 of the sort depicted in FIG. 10A and FIG. 10Bmay operate under the control of an operating system, which controlsscheduling of tasks and access to system resources. The computing device1500 may be running any operating system, any embedded operating system,any real-time operating system, any open source operating system, anyproprietary operating system, any operating systems for mobile computingdevices, or any other operating system capable of running on thecomputing device and performing the operations described herein.

The computing device 1500 may be any workstation, desktop computer,laptop or notebook computer, server machine, handheld computer, mobiletelephone or other portable telecommunication device, media playingdevice, gaming system, mobile computing device, or any other type and/orform of computing, telecommunications or media device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. In someembodiments, the computing device 1500 may have different processors,operating systems, and input devices consistent with the device.

In other embodiments the computing device 1500 is a mobile device, suchas a Java-enabled cellular telephone or personal digital assistant(PDA), a smart phone, a digital audio player, or a portable mediaplayer. In some embodiments, the computing device 1500 comprises acombination of devices, such as a mobile phone combined with a digitalaudio player or portable media player.

As shown in FIG. 10C, the central processing unit 1521 may comprisemultiple processors P1, P2, P3, P4, and may provide functionality forsimultaneous execution of instructions or for simultaneous execution ofone instruction on more than one piece of data. In some embodiments, thecomputing device 1500 may comprise a parallel processor with one or morecores. In one of these embodiments, the computing device 1500 is ashared memory parallel device, with multiple processors and/or multipleprocessor cores, accessing all available memory as a single globaladdress space. In another of these embodiments, the computing device1500 is a distributed memory parallel device with multiple processorseach accessing local memory only. In still another of these embodiments,the computing device 1500 has both some memory which is shared and somememory which may only be accessed by particular processors or subsets ofprocessors. In still even another of these embodiments, the centralprocessing unit 1521 comprises a multicore microprocessor, whichcombines two or more independent processors into a single package, e.g.,into a single integrated circuit (IC). In one exemplary embodiment,depicted in FIG. 10D, the computing device 1500 includes at least onecentral processing unit 1521 and at least one graphics processing unit1521′.

In some embodiments, a central processing unit 1521 provides singleinstruction, multiple data (SIMD) functionality, e.g., execution of asingle instruction simultaneously on multiple pieces of data. In otherembodiments, several processors in the central processing unit 1521 mayprovide functionality for execution of multiple instructionssimultaneously on multiple pieces of data (MIMD). In still otherembodiments, the central processing unit 1521 may use any combination ofSIMD and MIMD cores in a single device.

A computing device may be one of a plurality of machines connected by anetwork, or it may comprise a plurality of machines so connected. FIG.10E shows an exemplary network environment. The network environmentcomprises one or more local machines 1502 a, 1502 b (also generallyreferred to as local machine(s) 1502, client(s) 1502, client node(s)1502, client machine(s) 1502, client computer(s) 1502, client device(s)1502, endpoint(s) 1502, or endpoint node(s) 1502) in communication withone or more remote machines 1506 a, 1506 b, 1506 c (also generallyreferred to as server machine(s) 1506 or remote machine(s) 1506) via oneor more networks 1504. In some embodiments, a local machine 1502 has thecapacity to function as both a client node seeking access to resourcesprovided by a server machine and as a server machine providing access tohosted resources for other clients 1502 a, 1502 b. Although only twoclients 1502 and three server machines 1506 are illustrated in FIG. 10E,there may, in general, be an arbitrary number of each. The network 1504may be a local-area network (LAN), e.g., a private network such as acompany Intranet, a metropolitan area network (MAN), or a wide areanetwork (WAN), such as the Internet, or another public network, or acombination thereof.

The computing device 1500 may include a network interface 1518 tointerface to the network 1504 through a variety of connectionsincluding, but not limited to, standard telephone lines, local-areanetwork (LAN), or wide area network (WAN) links, broadband connections,wireless connections, or a combination of any or all of the above.Connections may be established using a variety of communicationprotocols. In one embodiment, the computing device 1500 communicateswith other computing devices 1500 via any type and/or form of gateway ortunneling protocol such as Secure Socket Layer (SSL) or Transport LayerSecurity (TLS). The network interface 1518 may comprise a built-innetwork adapter, such as a network interface card, suitable forinterfacing the computing device 1500 to any type of network capable ofcommunication and performing the operations described herein. An I/Odevice 1530 may be a bridge between the system bus 1550 and an externalcommunication bus.

According to one embodiment, the network environment of FIG. 10E may bea virtual network environment where the various components of thenetwork are virtualized. For example, the various machines 1502 may bevirtual machines implemented as a software-based computer running on aphysical machine. The virtual machines may share the same operatingsystem. In other embodiments, different operating system may be run oneach virtual machine instance. According to one embodiment, a“hypervisor” type of virtualization is implemented where multiplevirtual machines run on the same host physical machine, each acting asif it has its own dedicated box. Of course, the virtual machines mayalso run on different host physical machines.

Other types of virtualization is also contemplated, such as, forexample, the network (e.g. via Software Defined Networking (SDN)).Functions, such as functions of the session border controller and othertypes of functions, may also be virtualized, such as, for example, viaNetwork Functions Virtualization (NFV).

It is the Applicant's intention to cover by claims all such uses of theinvention and those changes and modifications which could be made to theembodiments of the invention herein chosen for the purpose of disclosurewithout departing from the spirit and scope of the invention. Theparticular manner in which template details are presented to the usermay also differ. Thus, the present embodiments of the invention shouldbe considered in all respects as illustrative and not restrictive, thescope of the invention to be indicated by claims and their equivalentsrather than the foregoing description.

The invention claimed is:
 1. A system for managing interactions of acustomer contact center, the system comprising: a processor; and amemory, wherein the memory has stored therein instructions that, whenexecuted by the processor, cause the processor to: receive data about aninteraction with an electronic device operated by a customer of thecustomer contact center; identify, based on profile data of thecustomer, the customer as having customer controlled interactionmanagement (CCIM) eligibility; receive, based on the customer having theCCIM eligibility, a command from the electronic device operated by thecustomer, the command comprising an instruction for routing theinteraction; identify a routing point for routing the interaction, therouting point being associated with routing logic that includes routinginstructions generated in response to command from the electronic deviceoperated by the customer; and route the interaction to the identifiedrouting point by invoking the routing logic for giving the customercontrol of the routing of the interaction.
 2. The system of claim 1,wherein the interaction is a telephony interaction, the system furthercomprising: a switch coupled to the processor for establishing a voicepath between the electronic device operated by the customer and a deviceof the customer contact center.
 3. The system of claim 1, wherein thereceived data includes a caller identifier.
 4. The system of claim 1,wherein the instructions further cause the processor to: transmit asoftware application to the electronic device operated by the customerover a communications network, wherein the software application includesinstructions for executing the routing logic.
 5. The system of claim 4,wherein the software application includes instructions for monitoringpresence of a device of the customer contact center.
 6. The system ofclaim 5, wherein the software application includes instructions forreceiving presence information from a contact center server.
 7. Thesystem of claim 4, wherein the software application is transmitted tothe electronic device operated by the customer in response toidentifying the customer as belonging to a particular customer segment.8. The system of claim 4, wherein the interaction is a telephonyinteraction, and the software application includes instructions forinvoking a dialer for initiating the telephony interaction.
 9. Thesystem of claim 4, wherein the software application provides aninterface for prompting the customer to configure the routing logic. 10.The system of claim 4, wherein the software application provides aninterface for prompting the customer to identify one or more preferredcontact center agents.
 11. The system of claim 4, wherein the softwareapplication provides an interface for prompting the customer to providea rating for the interaction.
 12. The system of claim 11, wherein thesoftware application is configured to share the rating with othercustomers.
 13. The system of claim 1, wherein the routing point isidentified by a telephone number.
 14. A method for managing interactionsof a customer contact center, the method comprising: receiving, by aprocessor, data about the interaction with an electronic device operatedby a customer of the customer contact center; identifying, by theprocessor, based on profile data of the customer, the customer as havingcustomer controlled interaction management (CCIM) eligibility; receive,by the processor, based on the customer having the CCIM eligibility, acommand from the electronic device operated by the customer, the commandcomprising an instruction for routing the interaction; identifying, bythe processor, a routing point for routing the interaction, the routingpoint being associated with routing logic that includes routinginstructions generated in response to command from the electronic deviceoperated by the customer; and routing the interaction to the identifiedrouting point by invoking the routing logic for giving the customercontrol of the routing of the interaction.
 15. The method of claim 14,wherein the interaction is a telephony interaction, and the methodfurther includes: establishing a voice path between the electronicdevice operated by the customer and a device of the customer contactcenter via a switch.
 16. The method of claim 14, wherein the receiveddata includes a caller identifier.
 17. The method of claim 14 furthercomprising: transmitting a software application to electronic deviceoperated by the customer over a communications network, wherein thesoftware application includes instructions for executing the routinglogic.
 18. The method of claim 17, wherein the software applicationmonitors presence of a device of the customer contact center.
 19. Themethod of claim 18, wherein the software application receives presenceinformation from a contact center server.
 20. The method of claim 17,wherein the software application is transmitted to the electronic deviceoperated by the customer in response to identifying the customer asbelonging to a particular customer segment.